Repository navigation
Modernize DevDiv static analysis pipeline - #26304
Stella Huang (StellaHuang95) merged 1 commit into
Conversation
Co-authored-by: Copilot App <223556219+Copilot@users.noreply.github.com>
|
🔒 Automated review in progress — Rich Chiodo (@rchiodo) is auto-reviewing this PR. |
|
Reviewed commit: Result: 🔴 Verification detailsVerification: Automated verification is best effort. The PR author remains responsible for testing. Summary: [unavailable] Container verification could not start and local execution was not authorized for this PR HEAD: C:\Users\rchiodo\AppData\Local\Programs\Podman\podman.EXE --connection pyrx-automation failed: stderr: Error: unable to start container "b5e216358f2f1b62fce387a32932c451fed1b3bd5ad26b19d2f5f718d19f1a17": crun: open `memory.max` for writing: No such file or directory: OCI runtime attempted to invoke a command that was not found Test runs: none recorded. |
Rich Chiodo (rchiodo)
left a comment
There was a problem hiding this comment.
Approved via Review Center.
f87ce4b
into
microsoft:main
Summary
AutoApplicability@1andVulnerabilityAssessment@0vscode-python-mainwhile keeping template TSA disabledBanditResultspipeline artifactCoverage
DevDiv run 16070997 showed both the 1ES AntiMalware source scan and the legacy explicit AntiMalware task, policy-injected component detection alongside the explicit component task, deprecation warnings for the old Guardian task majors, and a TSA 412 because
vscode-python-mainis retired for the WiM transition.The 1ES template now owns AntiMalware, Component Governance/Detection, CredScan, PoliCheck,
SdtReport, andPublishSecurityAnalysisLogswith its supported task versions. The template also owns eligible Advanced Security publication; this change does not addAdvancedSecurity-Publishmanually. Bandit remains explicit so its existing Guardian ruleset and exactpython_files/test exclusion target stay unchanged. Its SARIF is copied to a supported non-production 1ES pipeline output for post-run review.The supported 1ES PoliCheck surface does not expose the legacy
optionsRulesDBPathinput used forbuild/ci/static_analysis/policheck/exceptions.mdb, so that old task-only wiring is not carried forward. If that custom rules database is still required, it needs a supported 1ES/MicroBuild integration rather than another explicit legacy PoliCheck task.The Trust Services Automation/WiM support incident and any retired-codebase follow-up are being handled separately. This PR does not change API Scan, triggers, agent pools, release or product publishing, the live pipeline definition, or cutover.
Validation
build/azure-pipelines/devdiv/static-analysis.ymlwith PyYAMLprettier 2.0.2 --check build/azure-pipelines/devdiv/static-analysis.ymlgit diff --checkTracking: microsoft/pyrx#10073